Publisher: Activision
Call of Duty: World at War is Treyarch’s controversial World War II shooter set on the Pacific and Eastern fronts, where you switch roles between an American Marine and a Russian soldier who survives Stalingrad and follows the push into Berlin at the end of the war.
World at War uses a beefed up version of the proprietary engine used in
Call of Duty 4: Modern Warfare, which was developed by Infinity Ward and has easily been the most successful game in the series. It uses the DirectX 9.0 renderer exclusively and features true world dynamic lighting, HDR lighting, dynamic shadowing and depth of field amongst other things.
We used the full retail version of the game downloaded from Steam, which was patched to version 1.1 and for our gameplay testing, we did a 90-second manual run through from the second mission in the game where you are part of a beach landing in the Pacific. It appears to be one of the more intensive parts of the game with lots of explosions, water, smoke and lighting effects thrown in for good measure.
All of the in-game settings were set to their maximum values, including texture details which were configured to 'Extra'. The 'Dual Video Cards' option was enabled for the multi-GPU configurations, but was disabled for all single GPU cards. Finally, anti-aliasing and anisotropic filtering were controlled from inside the game.
-
Nvidia GeForce GTX 280 1GB SLI
-
Nvidia GeForce GTX 260-216 896MB SLI
-
Nvidia GeForce GTX 295 1,792MB
-
ATI Radeon HD 4870 1GB CrossFire
-
ATI Radeon HD 4870 X2 2GB
-
Zotac GeForce GTX 285 1GB AMP!
-
Nvidia GeForce GTX 285 1GB
-
Nvidia GeForce GTX 280 1GB
-
Nvidia GeForce GTX 260-216 896MB
-
ATI Radeon HD 4870 512MB
-
ATI Radeon HD 4870 1GB
Frames Per Second
-
Nvidia GeForce GTX 280 1GB SLI
-
Nvidia GeForce GTX 260-216 896MB SLI
-
Nvidia GeForce GTX 295 1,792MB
-
ATI Radeon HD 4870 1GB CrossFire
-
Zotac GeForce GTX 285 1GB AMP!
-
ATI Radeon HD 4870 X2 2GB
-
Nvidia GeForce GTX 285 1GB
-
Nvidia GeForce GTX 280 1GB
-
Nvidia GeForce GTX 260-216 896MB
-
ATI Radeon HD 4870 1GB
-
ATI Radeon HD 4870 512MB
Frames Per Second
-
Nvidia GeForce GTX 280 1GB SLI
-
Nvidia GeForce GTX 260-216 896MB SLI
-
Nvidia GeForce GTX 295 1,792MB
-
ATI Radeon HD 4870 1GB CrossFire
-
Zotac GeForce GTX 285 1GB AMP!
-
ATI Radeon HD 4870 X2 2GB
-
Nvidia GeForce GTX 285 1GB
-
Nvidia GeForce GTX 280 1GB
-
Nvidia GeForce GTX 260-216 896MB
-
ATI Radeon HD 4870 1GB
-
ATI Radeon HD 4870 512MB
0
10
20
30
40
50
60
70
80
90
Frames Per Second
-
Nvidia GeForce GTX 280 1GB SLI
-
Nvidia GeForce GTX 295 1,792MB
-
Nvidia GeForce GTX 260-216 896MB SLI
-
Zotac GeForce GTX 285 1GB AMP!
-
Nvidia GeForce GTX 285 1GB
-
ATI Radeon HD 4870 1GB CrossFire
-
ATI Radeon HD 4870 X2 2GB
-
Nvidia GeForce GTX 280 1GB
-
Nvidia GeForce GTX 260-216 896MB
-
ATI Radeon HD 4870 1GB
-
ATI Radeon HD 4870 512MB
0
10
20
30
40
50
60
70
80
90
Frames Per Second
-
Nvidia GeForce GTX 280 1GB SLI
-
Nvidia GeForce GTX 295 1,792MB
-
Nvidia GeForce GTX 260-216 896MB SLI
-
ATI Radeon HD 4870 1GB CrossFire
-
Zotac GeForce GTX 285 1GB AMP!
-
Nvidia GeForce GTX 280 1GB
-
ATI Radeon HD 4870 X2 2GB
-
Nvidia GeForce GTX 285 1GB
-
Nvidia GeForce GTX 260+-216 896MB
-
ATI Radeon HD 4870 1GB
-
ATI Radeon HD 4870 512MB
0
10
20
30
40
50
60
70
80
Frames Per Second
-
Nvidia GeForce GTX 280 1GB SLI
-
Nvidia GeForce GTX 295 1,792MB
-
Nvidia GeForce GTX 260-216 896MB SLI
-
Zotac GeForce GTX 285 1GB AMP!
-
Nvidia GeForce GTX 285 1GB
-
ATI Radeon HD 4870 1GB CrossFire
-
ATI Radeon HD 4870 X2 2GB
-
Nvidia GeForce GTX 280 1GB
-
Nvidia GeForce GTX 260-216 896MB
-
ATI Radeon HD 4870 1GB
-
ATI Radeon HD 4870 512MB
0
10
20
30
40
50
60
70
80
Frames Per Second
World at War is an interesting beast because the GeForce GTX 285 runs into the Radeon HD 4870 X2 here because the ATI Catalyst drivers don't scale particularly well in this title. Despite this though, we did encounter a driver bug at 2,560 x 1,600 2xAA, where the performance was actually
lower than it was at 2,560 x 1,600 4xAA - we've informed Nvidia of our findings and it says that it is working to find out what the issue is.
Want to comment? Please log in.